Compose posts reach the command history; the pane's tab chord becomes findable - #34

Two independent changes, one commit each.

fix(compose) — a post you wrote is a post you can recall

The F1 composer's ⌃S called the session's send directly and skipped OnCommandEntered, which holds the one seam in the client that adds a history entry. A composed post was therefore echoed and alias-expanded — both free from SendUserInputAsync — and never recorded, so ⌥↑ and ⌃R could not reach it. SendComposed's own doc had claimed all three for as long as the composer existed.

It is not consistency-by-design. The rule elsewhere is history records what was entered on a command line, not what was sent: /web is in it and a macro is not, and the auto-login's exclusion is deliberate and pinned. A composed post is a command the user just wrote, and it was the only user-authored command in this client with no recall route at all.

It keeps going direct rather than being routed through OnCommandEntered, which is the command line's seam: that also clears the window's bar draft, moves the unsent marker and owns the /web, /graphics and /triggers branches, none of which belong to a post written elsewhere. It records the entry itself instead — the built line rather than the buffer, since history holds sendable commands and a recalled entry lands on a one-command bar — and through InputHistory.Add, so a post carrying a connect line meets the same secret gate.

Paste into the composer was checked and is fine: it reaches MultilineEditControl through the framework's IPasteTarget path, newlines survive SanitizeInputText, and a multi-line paste survives the %r join.

feat(tabs) — the key that walks a pane's tabs can now be found

⌃N has cycled the focused pane's tab strip for as long as panes have held more than one window. It was named on F4 and nowhere else — no ⌃P entry, no status-row hint, nothing on the strip itself.

The chord stays ⌃N, and the familiar alternatives were measured rather than assumed — driven at a raw-mode reader with kitten @ send-key:

⌥Tab would additionally need a TryAltEnter-style reassembly on a key already spent as TerminalFocusWatcher's disguised focus-in, and send-key writes into the pty, so it says nothing about the compositor — which takes ⌥Tab unconditionally on Windows, GNOME and KDE. The reported problem was that ⌃N could not be found, not that it was wrong, so no chord was spent.

What changed:

• A ⌃P entry, layout:next-tab / Focus the next tab / ⌃N, listed unconditionally like the directional pane entries beside it — this surface is where a reader learns a pane holds tabs at all.
• A status-row segment, ⌃N tab, shown exactly while the focused pane has a second tab, following the same contextual rule as the pane and second-bar hints.
• NextWindow refuses out loud. It returned in silence on a single-tab pane, which is indistinguishable from a dead key; listing a key on a surface obliges it to answer, which every directional entry beside it already does. Wording sits beside PrefixPanel.NoCycleRefusal.
• One vocabulary. F4 and --help said window while everything else said tab; ⌥N already owns the window noun, and two keys described in the same noun read as two spellings of one action.
• FocusHints is generated from a segment list instead of eight hand-written ladders (three independent conditions), with reading order and drop order kept separate — the row reads pane · size · line while size is the first thing surrendered, so dropping from the end of the reading order would have silently reordered it. Verified: the split and focus frames are unchanged cell for cell; the default frame gains ⌃N tab and is still exactly 120 cells.

Verification

dotnet build -c Release SharpMUTerm.slnx warning-free; all five suites green (Core 938, Tui 1786, Graphics 83, Scripting 42, Web 37 — 2,886). Frames rendered and read: default, split, focus, tint-tabs.

🤖 Generated with Claude Code

https://claude.ai/code/session_015nuKnWthnELNkrd86q5KWN

Summary by CodeRabbit

• New Features

  • Added Ctrl+N support for switching to the next tab in the focused pane, including wraparound navigation.
  • Added the shortcut to the command palette, help text, and status hints.
  • Improved contextual focus hints to adapt to available screen space.

• Bug Fixes

  • Clearly reports when tab switching is unavailable in a single-tab pane.
  • Successfully sent composed posts can now be recalled from command history.

• Documentation

  • Updated tab-navigation documentation and terminology.